Alberto Garcia [Mon, 5 May 2025 15:28:28 +0000 (17:28 +0200)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Mon, 5 May 2025 15:28:28 +0000 (17:28 +0200)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Thu, 3 Apr 2025 20:45:28 +0000 (20:45 +0000)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Thu, 3 Apr 2025 20:45:28 +0000 (20:45 +0000)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Thu, 3 Apr 2025 17:27:40 +0000 (19:27 +0200)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Thu, 3 Apr 2025 17:27:40 +0000 (19:27 +0200)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Thu, 3 Apr 2025 17:27:40 +0000 (19:27 +0200)]
wpewebkit (2.48.1-1) unstable; urgency=high
* New upstream release.
* debian/rules:
- Build with -mlarge-data and -mlarge-text on alpha (see #1101547).
- Build with HAVE_DENORMAL=0 on armel (WebKit bug #290994).
* Refresh all patches and drop fix-soname.patch.
* debian/control:
- Update Standards-Version to 4.7.2 (no changes).
Alberto Garcia [Mon, 17 Mar 2025 00:50:25 +0000 (01:50 +0100)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Mon, 17 Mar 2025 00:50:25 +0000 (01:50 +0100)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Sun, 9 Feb 2025 17:32:24 +0000 (18:32 +0100)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Sun, 9 Feb 2025 17:32:24 +0000 (18:32 +0100)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Sun, 9 Feb 2025 17:32:24 +0000 (18:32 +0100)]
wpewebkit (2.46.6-1) unstable; urgency=high
* New upstream release.
* Update copyright information of all files.
* debian/rules:
- Stop using -DWTF_CPU_ARM64_CORTEXA53=OFF, this was fixed upstream a
long time ago (WebKit bug #197192).
* debian/upstream/signing-key.asc:
- sq complains about multiple concatenated ASCII Armor blocks, so put
all keys in the same block.
Alberto Garcia [Thu, 19 Dec 2024 00:18:46 +0000 (01:18 +0100)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Thu, 19 Dec 2024 00:18:46 +0000 (01:18 +0100)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 27 Nov 2024 13:43:44 +0000 (14:43 +0100)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 27 Nov 2024 13:43:44 +0000 (14:43 +0100)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 27 Nov 2024 13:43:44 +0000 (14:43 +0100)]
wpewebkit (2.46.4-1) unstable; urgency=high
* New upstream release.
* The WPE WebKit security advisory WSA-2024-0007 lists the following
security fixes in the latest versions of WPE WebKit:
- CVE-2024-44308, CVE-2024-44309 (fixed in 2.46.4).
Alberto Garcia [Wed, 30 Oct 2024 21:57:37 +0000 (22:57 +0100)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 30 Oct 2024 21:57:37 +0000 (22:57 +0100)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Tue, 22 Oct 2024 11:22:44 +0000 (13:22 +0200)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Tue, 22 Oct 2024 11:22:44 +0000 (13:22 +0200)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 2 Oct 2024 16:54:49 +0000 (18:54 +0200)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 2 Oct 2024 16:54:49 +0000 (18:54 +0200)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 2 Oct 2024 16:54:49 +0000 (18:54 +0200)]
wpewebkit (2.46.1-1) unstable; urgency=medium
* New upstream release.
* Remove the following patches:
- prefer-pthread.patch: this should not be needed anymore.
- reduce-memory-overheads.patch: Override LDFLAGS instead.
* debian/patches/dont-detect-sse2.patch:
- Update this patch.
* Update copyright information of all files.
* debian/libwpewebkit-2.0-1.symbols:
- Update symbols.
* debian/source/lintian-overrides:
- Update source-is-missing overrides.
* debian/rules:
- Remove compiler overrides for sh4 (see #1082305).
- Stop limiting parallel builds on Ubuntu.
Alberto Garcia [Fri, 6 Sep 2024 14:59:28 +0000 (16:59 +0200)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Fri, 6 Sep 2024 14:59:28 +0000 (16:59 +0200)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Fri, 6 Sep 2024 14:59:28 +0000 (16:59 +0200)]
wpewebkit (2.44.4-1) unstable; urgency=medium
* New upstream release.
* Drop fix-clang-build.patch and fix-webasm-crash.patch.
* debian/rules:
- Disable dh_dwz, it breaks the build in at least i386 and amd64
(see #1081000).
Alberto Garcia [Mon, 26 Aug 2024 15:14:46 +0000 (17:14 +0200)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Mon, 26 Aug 2024 15:14:46 +0000 (17:14 +0200)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
projects / wpewebkit.git / log